System and method for scoping searches using index keys

ABSTRACT

A set of index keys is included in an index search system that are associated with the scope of the search rather than the content of the documents that are the target of the search. These scope related index keys, or scope keys allows the scope of the search to be selected, reducing the number of documents that a search is required to sift through to obtain results. Furthermore, compound scopes are recognized and stored such that an index of complex search scopes is provided to eliminate rehashing of the searches based on these complex search scopes.

BACKGROUND OF THE INVENTION

Searches among networks and file systems for content have been providedin many forms but most commonly by a variant of a search engine. Asearch engine is a program that searches documents for specifiedkeywords and returns a list of the documents where the keywords werefound.

Typically, a search engine works by sending out a spider to fetch asmany documents as possible. Another program, called an indexer, thenreads these documents and creates an index based on the words containedin each document. An index is a list of keys or keywords, each of whichidentifies a unique record. Indices make it faster to find specificrecords and to sort records by the index field. A search engine uses analgorithm to create its indices such that, ideally, only meaningfulresults are returned for each query by a client or user.

A fairly consistent aspect of these queries is the use of a keyword orindex key. Whether a user enters a search query as a long text string ora connection of Boolean operators, the search engine examines allrecords for the keywords entered corresponding to documents that matchthe keywords. A subset of the records is then returned that satisfiesthe Boolean operator constraints or corresponds to the long text string.Examining these records can be a time consuming and expensive operation.In addition, a client may not desire a full record search for documentscontaining a particular keyword.

SUMMARY OF THE INVENTION

Embodiments of the present invention are related to a system and methodthat solves for the above mentioned limitations by providing a class ofindex keys, referred to as scope keys, that define a scope of the searchrather than merely providing a keyword. When a scope key is entered in asearch query, the scope key limits the scope of the index recordssearched. For example, a scope key can limit the scope of a search bylimiting the search results to a certain file type, such as .mpg files.Another scope key can limit the scope of search according to a URL(Uniform Resource Locator) so that only documents under that URL aresearched. Still another scope key may limit the scope of the search to aparticular database on the user's computer or other networked computer.The present invention therefore solves the above-mentioned problem bysignificantly reducing the time and expense of a search by allowing theuser to limit the scope for the search using a particular class of indexkeys.

In accordance with another aspect of the present invention, compoundscopes are also recognized and stored. This additional index partitionincludes scope definitions that are combinations of the basic scopes.The documents corresponding to these compound scopes have already beenresolved, allowing for faster searches when these compound scopes arereferenced.

BRIEF DESCRIPTION OF THE INVENTION

FIG. 1 illustrates an exemplary computing device that may be used in oneexemplary embodiment of the present invention.

FIG. 2 illustrates a block diagram of an exemplary system for scopingsearches using index keys in accordance with the present invention.

FIG. 3 illustrates a block diagram for an exemplary structure of anindex in accordance with the present invention.

FIG. 4 illustrates an exemplary block diagram for managing compoundscopes in accordance with the present invention.

FIG. 5 illustrates a logical flow diagram of an exemplary process forgenerating an index in accordance with the present invention.

FIG. 6 illustrates a logical flow diagram of an exemplary process forcompiling an index in accordance with the present invention.

FIG. 7 illustrates a logical flow diagram of an exemplary process forhandling a query in accordance with the present invention.

DETAILED DESCRIPTION

The present invention now will be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific exemplary embodiments forpracticing the invention. This invention may, however, be embodied inmany different forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the invention to those skilled in the art. Amongother things, the present invention may be embodied as methods ordevices. Accordingly, the present invention may take the form of anentirely hardware embodiment, an entirely software embodiment or anembodiment combining software and hardware aspects. The followingdetailed description is, therefore, not to be taken in a limiting sense.

Illustrative Operating Environment

With reference to FIG. 1, one exemplary system for implementing theinvention includes a computing device, such as computing device 100.Computing device 100 may be configured as a client, a server, mobiledevice, or any other computing device. In a very basic configuration,computing device 100 typically includes at least one processing unit 102and system memory 104. Depending on the exact configuration and type ofcomputing device, system memory 104 may be volatile (such as RAM),non-volatile (such as ROM, flash memory, etc.) or some combination ofthe two. System memory 104 typically includes an operating system 105,one or more applications 106, and may include program data 107. In oneembodiment, application 106 includes a search scoping application 120for implementing the functionality of the present invention. This basicconfiguration is illustrated in FIG. 1 by those components within dashedline 108.

Computing device 100 may have additional features or functionality. Forexample, computing device 100 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 1 by removable storage 109 and non-removable storage 110. Computerstorage media may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. System memory 104, removable storage 109and non-removable storage 110 are all examples of computer storagemedia. Computer storage media includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by computing device 100. Any such computerstorage media may be part of device 100. Computing device 100 may alsohave input device(s) 112 such as keyboard, mouse, pen, voice inputdevice, touch input device, etc. Output device(s) 114 such as a display,speakers, printer, etc. may also be included.

Computing device 100 also contains communication connections 116 thatallow the device to communicate with other computing devices 118, suchas over a network. Communication connection 116 is one example ofcommunication media. Communication media may typically be embodied bycomputer readable instructions, data structures, program modules, orother data in a modulated data signal, such as a carrier wave or othertransport mechanism, and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. The term computer readable media as used herein includesboth storage media and communication media.

Illustrative Embodiment for Scoping Searches

Throughout the following description and the claims, the term “document”refers to any possible resource that may be returned as the result of asearch query or crawl of a network, such as network documents, files,folders, web pages, and other resources. The term “index key” refers toany keyword or key associated with a search that is used to target a setof documents in a search query or creation of an index. The term “scopekey” refers to any index key that may be used to narrow the scope of thesearch such that the number of documents to be search is reduced beforethe search is commenced. The scope of the search can be narrowedaccording to attributes such as file types, locations such as certaindatabases or URLs, or by other criteria that reduces the number ofdocuments to be searched.

Embodiments of the present invention are related to increasing the queryefficiency of all scoped queries by representing the scopes of each itemin the index with scope keys and adding the appropriate scope key to thequery as another restriction. This method is provided in contrast to amethod that re-calculates the scope condition for every documentmatching the user keywords based on document properties (e.g., URL orother metadata). Since most scopes will represent a narrow slice of theset of all crawled items, the efficiency of scoped queries is increasedby a factor less than but related to the narrowness of that slice. Inone example, an administrator of a portal (i.e., a web site that offersa host of services including searches) may determine that the users ofthe portal are especially interested in functional specs. It maytherefore be advantageous to provide a search mechanism that onlysearches through these specs for keywords without sifting through thechaff of those words in other documents. Through an administrativeinterface the administrator may define a scope having a rule:profile=“spec”, or this scope may already be defined as a basic scope.The administrator may use the basic scope to define a compound scopehaving a rule: profile=“spec” AND filetype=“Text” AND author!=“JohnDoe”. After giving this scope a friendly name for the client's userinterface, and specifying from which sites this scope is available, thescope appears in the drop-down scope list for clients. This scopeselection returns only documents with that property value as queryresults. Scopes defined by an administrator in this manner may also bereferred to as authored scopes.

In addition, several default scope selection may be available. A typicalclient may be presented with an option to search “all content”, whichsimply indicates a non-scoped query. A scope selection for “this site”searches all documents on the current site and its subsites. A scope mayalso be generated that excludes certain results rather than simplyidentifying the scope for documents included within a particular subset.For example, a scope definition may correspond to a search for alldocument types except text (.txt) documents. Another scope definitionmay correspond to a search for all documents in a network except forthose associate with a particular Web Site URL. The number of scopeselections, whether default, authored, or otherwise are not limited tothose described herein.

In another embodiment, a client is also given the option to enter scopekeys directly into a search request. The scope key is given a name forease of use by the client, typing the name into the search requestlimits the search by the associated scope.

FIG. 2 illustrates a functional block diagram of an exemplary system forscoping searches using index keys in accordance with the presentinvention. System 200 includes index 210, pipeline 220, documentinterface 230, client interface 240, scopes plugin 250, indexing plugin260, scope descriptions 270, and administrative interface 280.

Index 210 is structured to include separate indexes for the content keys(i.e., keywords) and for the scope keys. A more detailed description ofthe structure of index 210 is provided below in the discussion of FIG.3. The records of these indexes are used to in providing results toclient queries. In one embodiment, index 210 corresponds to multipledatabases that collectively provide the storage for the index records.

Pipeline 220 is an illustrative representation of the gatheringmechanism for obtaining the documents or records of the documents forindexing. Pipeline 220 allows for filtering of data by various plugins(e.g., scopes plugin 250) before the records corresponding to the dataare entered into index 210.

Document interface 230 provides the protocols, network access points,and database access points for retrieving documents across multipledatabases and network locations. For example, document interface 230 mayprovide access to the Internet while also providing access to a databaseof a local server and access to a database on the current computingdevice. Other embodiments may access other document locations using avariety of protocols without departing from the spirit or scope of theinvention.

Client Interface 240 provides access by a client to define and initiatea search. The search may be defined according to keywords and/or scopekeys. An exemplary method for processing search queries is described ingreater detail in the discussion of FIG. 7 below.

Scopes plugin 250 is one of several gatherer pipeline plugins. Scopesplugin 250 identifies property values that are to be reemitted as scopekeys (i.e., items to be indexed in the scopes index). Those propertiesthat are identified as interesting properties relative to scope (e.g.,file types, URLs, etc.) are gathered by scope plugin 250 as thedocuments provided through document interface 230 are crawled. Theseproperties are reemitted by scope plugin 250 into pipeline 220 to beincluded in index 210. These properties are also usable by anadministrator or other entity for providing scope selections to a clientaccording to these properties.

Indexing plugin 260 is another plugin connected to pipeline 220.Indexing plugin provides the mechanism for generating, partitioning, andupdating index 210. An exemplary method for generating index 210 isdescribed in greater detail in the discussion of FIG. 5 below. Anexemplary method for updating index 210 is described in greater detailin the discussion of FIG. 6 below. In one embodiment, indexing plugin260 provides word lists that temporarily cache the keywords and scopekeys generated from crawled documents before flushing these results toindex 210. The records of index 210 are populated from the crawl resultsincluded in these word lists.

Scope descriptions 270 provides tables that store information about thescopes. For example, scope descriptions 270 may include administrativeinformation and internal information, such as scopes, scope rules,visibility, and other attributes corresponding to the scope relatedproperties and scope selections generated for use in search queries.Scope descriptions 270 receives the properties for generating the scopeselections through scope plugin 250. Scope descriptions 270 is alsoaccessed by indexing plugin 260 for generation and organization of thescope index within index 210. Index 210 also accesses scope descriptions270 for generation and update of the compound scope index (see FIGS. 3and 4 below). Scope descriptions is also accessed at client interface240, so that a client may select a scope for inclusion in a search queryor select a scope selection to apply to a search.

Administrative interface 280 also access scope descriptions 270 to allowan administrator or other control mechanism (e.g., automated program) totake the properties provided by scopes plugin 250 and create the scopeselections for use search queries. Administrative interface 280 may beprovided according to any format that allows the creation of the scopeselections and manipulation of the scope descriptions, (e.g., viaInternet login access).

Despite the illustration in system 200 of one-way and two-waycommunications between functional blocks, any of these communicationtypes may be changed to another type without departing from the spiritor scope of the invention (e.g., all communications may have anacknowledgment message requiring two-way rather than one-waycommunication).

FIG. 3 illustrates a functional block diagram for an exemplary structureof an index in accordance with the present invention. Index 300 includescontent index (.ci) 310, basic scopes index (.bsi) 320, and compoundscopes index (.csi) 330.

Content index 310 includes records organized in an inverted index thatlists documents that correspond to the keywords and other index keysused in the search query.. The scope keys however, are diverted to basicscopes index 320.

Basic scopes index 320 includes records of documents that correspond tobasic scopes. Basic scopes generally refer to scope selections thatcorrespond to a singular scope related property of a document. Forexample, the numeric ID of a document crawled on sitehttp://www.example.com would be recorded in the document list for ascope key which was composed by scopes plugin 250 to embody the property(site) and value (“example.com”).

Compound scopes index 330 includes scopes that are generated fromcombinations of the basic scopes in basic scopes index 320. For example,a compound scope may includes records of documents that are a particularfile type that are also related to a particular URL.

FIG. 4 illustrates an exemplary block diagram for managing compoundscopes in accordance with the present invention. Block diagram 400includes basic scope index 410, original compound scopes index 420, andnew compound scopes index 430.

When the basic scopes index is updated with additional basic scopes (seeFIG. 6 below), the compound scopes index must also be updated. Positionline 422 of original compound scopes index 420 illustrates the positionwhere the new compound scopes should be included. A copy of originalcompound scopes index 420 is made, producing new compound scopes index430. The copy of the original compound scopes index 420 is made untilthe position where the new compound scopes should be included isreached. New compound scopes 432 are then written into new compoundscopes index 430. After new compound scopes 432 are included, copying oforiginal compound scopes index 420 continues. The compound scopes 434that follow new compound scopes 432 are copied from original compoundscopes index 420 with an offset that compensates for the inclusion ofnew compound scopes 432.

FIG. 5 illustrates a logical flow diagram of an exemplary process forgenerating an index in accordance with the present invention. Process500 starts at block 502 where access is provided to a corpus ofdocuments. Processing continues at block 504.

At block 504, the corpus of documents are crawled to determine thedocuments that exist as well as properties (e.g., file type) that areassociated with those documents. An identifier or ID for each of thedocuments and their associated property are then forwarded as results ofthe crawl. Processing continues at block 506.

At block 506, the properties associated with the documents that relateto scope are obtained by a scopes plugin. The scopes plugin createsscope definitions from the properties. The scope definitions are usableby an administrator to create scope selections that allow a client tolimit a search according to its scope. Processing moves to block 508.

At block 508, the scope definitions created from the obtained propertiesare emitted as scope keys amongst the results of the crawl. These scopekeys operate similarly to the keywords and other index keys generatedfrom the crawl, while being directed to the scope of the search ratherthan content of the documents. Some of the properties that are obtainedfor generating the scope keys include the document type, the URL of thedocument, the document's author, and other properties. The scope key isgenerated to include an identifier (ID) of the type of scope key and atext string that identifies the particular scope key. For example, ifthe ID for scope keys related URL is 237, then a scope key correspondingto the document in http://www.example.com would be “[237]http://www.example.com”. This scope key is emitted into the pipeline andis subsequently associated with the document in the index. Once thescope keys are emitted, processing continues at block 510.

At block 510, the scope keys, keywords, and other accumulated propertiesfound in all the documents are flushed to the index. The flush writesthe keys and properties to disk. During the flush, the scope keys areseparated and sent to the basic scopes index, while the remaining datais sent to the content index. Processing continues at block 512.

At block 512, the compound scopes index is generated within the index.In one embodiment, the compound scopes index generated in response to acompilation process that is commenced for the index. One exemplaryprocess used for generating the compound scopes index is described inthe discussion of FIG. 6 below. In one embodiment, compound scopes aredefined by queries from clients. In another embodiment, a list ofcompound scopes is generated by an administrator before the index wasinstantiated. Once the compound scopes index is generated, processingcontinues to block 514, where process 500 ends.

In one embodiment, the basic scopes index is populated as the crawl iscommenced, but the compound scopes index is not populated until thecrawl is complete and the basic scopes index is fully built. Waiting tobuild the compound scopes index reduces overhead by reducing the queriesto the basic scopes index.

FIG. 6 illustrates a logical flow diagram of an exemplary process forcompiling an index in accordance with the present invention. Process 600starts at block 602 where the compilation process is commenced. In oneembodiment, process 600 is started asynchronously at a certain timeinterval (e.g., every 15 minutes) to update any existing compoundscopes. In another embodiment, process 600 is started when process 500of FIG. 5 enters block 512 to generate the compound scopes index fromthe newly generated basic scopes index. In still another embodiment,process 600 is commenced in response to other flushes to the index. Onceprocess 600 is commenced, processing continues at decision block 604.

At decision block 604 a determination is made whether a change recordcorresponding to each scope within the compound scopes index indicatesthat the current compound scope has changed. In one embodiment, asimilar process is used for generating the compound scopes index for thefirst time with a default setting that assumes all scopes have changed.Accordingly, generating a new compound scopes index and updating acompound scopes index are handled by the same compilation process. Ifthe compound scope has changed, processing moves to block 406.

At block 606, a compilation process executes a query that is similar toa user query and allows the query process to update the list ofdocuments corresponding to the scope in the compound scopes index. Thelist of documents is then appended to into compound scopes index as thecompound scopes index is copied from its previous version (when aprevious version exists). Processing continues at decision block 610.

Alternatively, if the change record indicates that the particular scopehas not changed, processing moves to block 608. At block 608, the listof document IDs corresponding to the scope in the previous version ofthe compound scopes index is copied verbatim since the scope has notchanged. Processing continues at decision block 610.

At decision block 610, a determination is made whether more compoundscopes need to be copied to the new compound scopes index during thecompilation process. If more compound scopes are to be copied,processing returns to decision block 610 to determine if the compoundsscopes have changed. However, if no more compound scopes need to betransferred to the new compound scopes index, processing moves to block612, where process 600 ends.

Updates to the corpus of documents may occur at any time. The documentIDs for the corpus of documents are continually updated in an in-memoryword list or multiple word lists. The population of the word listresults from either initiated searches by clients, refresh actions thatcause the corpus to be recrawled, or other various operations that leadto discovery of the change among the corpus of documents. When adocument is changed (e.g., add, delete, modify), the document ID for thechanged document is then forwarded to the in-memory word list along withthe type of change. The word lists with the updated document IDs arethen flushed to the index. The change to the document results in anupdate to the content index while the basic scopes index is alsoupdated. Once the incremental crawl that discovered the change iscomplete, and the basic scopes index is updated, the compound scopesindex is also updated to reflect the change to the documents on thenetwork. Process 600 is used to reflect the updates in the compoundscopes index independent of whether the update is a new document amongstthe corpus of documents that are searched, a removal of a document fromthe corpus, or a modification to a document that effects the document'sscope. By running the complication process asynchronously, every sooften the compound scopes index is updated to reflect the changes to thedocuments on the network.

FIG. 7 illustrates a logical flow diagram of an exemplary process forhandling a query in accordance with the present invention. Process 700starts at block 702 where the index is instantiated and ready to accepta query from a client. Processing continues at decision block 704.

At decision block 704, a determination is made whether a search queryhas been initiated by a client. The client may correspond to a user thatinitiates a query or a program that is requesting the search. If asearch has not been initiated, processing loops back onto block 704while waiting for a search query to be initiated. However, once a searchquery is commenced, processing continues at decision block 706.

At decision block 706, a determination is made whether a scope key hasbeen used in the search request. If there is no scope key present,processing advances to block 716. However, if a scope key is present inthe search request, processing continues at decision block 708.

At decision block 708, a determination is made whether the instance ofthe scope key is as a portion of a compound scope. If the scope key isnot used as part of a compound scope, processing advances to decisionblock 712. However, if the scope key is part of a compound scope,processing moves to block 710.

At block 710, the compound scopes index (.csi) is consulted for thedocuments identified by their document IDs as corresponding the compoundscope included in the search query. The document IDs corresponding tothese documents are then returned to be added to the search resultspending the finalization of the search. Processing continues at decisionblock 712.

At decision block 712, a determination is made whether the instance ofthe scope key is as a portion of a compound scope. If the scope key doesnot correspond to a basic scope, processing advances to block 716.However, if the scope key does correspond to a basic scope, processingmoves to block 714.

At block 714, the basic scopes index (.bsi) is consulted for thedocuments identified by their document IDs as corresponding the scopekey included in the search query. The document IDs corresponding tothese documents are then returned to be added to the search resultspending the finalization of the search. Processing continues at decisionblock 716.

At decision block 716, a determination is made whether a keyword orother index key related to the content of documents is included in thesearch request. If a keyword is not included in the search request,processing advances to decision block 720. However if a keyword isincluded in the search request, processing moves to block 718.

At block 708, the content index (.ci) is consulted for the documentsidentified by their document IDs as corresponding the keyword includedin the search query. In one embodiment, as the content index is searchfor the keyword, the search is limited to the scope previously definedaccording to the basic scopes index and/or the compound scopes index.The document IDs corresponding to these documents are then returned tobe added to the search results pending the finalization of the search.Processing continues at decision block 710.

At block 720, the collection of document IDs for documents thatoverlapped in the different index partitions are returned as the queryresults. For example, the document ID may be correspond to a scope ofthe basic scopes index and also include a particular keyword. If thesearch request was limited by this particular scope and included thekeyword, then the document ID would overlap between the indexpartitions. These overlapping IDs represent the results of the search. Apointer to each document included in the results can then be provided tothe client in response to the search request. Typically, it is muchfaster to determine overlapping documents among indexes instead ofconsulting document properties to verify if the document is with anparticular scope. Where document properties are generally located atrandom within a database, the index is clustered on a disk according tothe keys (scope keys or keywords). The present invention thereforegreatly increases the speed and ease by which a scope can be applied toa search query. Once the results are provided, processing moves to block722, where process 700 ends.

In one embodiment, the process steps provided in operational blocks708-718 are not sequential. Instead the basic scopes index or thecompound scopes index or the content index are consulted based on theregular keys and scope keys of the query and the order they areconsulted in depends on the sort order of the document IDs thatcorrespond to the keys. In addition, the process steps provided inoperational blocks 708-718 may need to be repeated multiple times asthere may be multiple scopes, both compound scopes and basic scopes,included in a search query.

In another embodiment, the compound scopes index is updated with a newcompound scope after each search request if a new compound scope iscreated by the request. The compound scopes index is updated accordingthe method provided in the discussion of FIG. 4 above.

In still another embodiment, the scoped portion of a search request is asearch selection made by the client. The search selection corresponds toa pre-selected scope of the results according to a list of scopesprovided. This list of scopes may be generated by an administratoraccording to the scope definitions.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

1. A computer-implemented method for establishing a search scope for aquery of documents, comprising: identifying a property related to thedocuments, the property being associated with a scope of the documents;generating a scope-related index key according to the identifiedproperty, wherein the scope-related index key is emitted among a set ofother index keys associated with a crawl of the documents; andgenerating an index that includes a document record that corresponds tothe scope-related index key, wherein the document record is used inproviding results to the query such that the search scope of the queryis related to the scope-related index key when the query is authored toincluded the search scope.
 2. The computer-implemented method of claim1, wherein the index includes a first partition corresponding to indexkeys that are related to content of the documents and a second partitionthat corresponds to the scope-related index keys.
 3. Thecomputer-implemented method of claim 2, wherein the index furtherincludes a third partition that includes additional document recordsorganized according to combinations of the scope-related index keys suchthat another search scope is defined by the combination.
 4. Thecomputer-implemented method of claim 3, wherein the combination of thescope-related index keys corresponds to a Boolean combination.
 5. Thecomputer-implemented method of claim 1, wherein the index includes apartition that includes additional document records organized accordingto combinations of the scope-related index keys such that another searchscope is defined by the combination.
 6. The computer-implemented methodof claim 5, wherein the partition is updated when a new combination ofscope-related index keys is created by copying the partition to create anew partition while inserting the document records into the newpartition that correspond to the new combination.
 7. Thecomputer-implemented method of claim 1, wherein a change amongst thedocuments that are queried causes an update to the index such that anadditional document record is associated with the scope-related indexkey in the index when the additional document is associated with theproperty, wherein the change corresponds to at least one of new documentinserted amongst the documents, a document amongst the documents beingremoved, and a modification to a document amongst the documents.
 8. Thecomputer-implemented method of claim 1, wherein the document recordincludes a document identifier that identifies the document for thequery.
 9. The computer-implemented method of claim 1, further comprisinggenerating a scope selection according to the scope-related index keysuch that the scope selection is selectable by a client for providing ascope to a client generated query.
 10. The computer-implemented methodof claim 1, further comprising providing an interface for manuallygenerating and manipulating additional scope-related index keys fromadditional properties associated with additional search scopes of thedocuments.
 11. A system for establishing a search scope for a query ofdocuments, comprising: a scopes plugin that is configured to identify aproperty related to the documents that is associated with a scope of thedocuments and generate a scope-related index key according to theidentified property, wherein the scope-related index key is emittedamong a set of other index keys associated with a crawl of thedocuments; and an index that is configured to include a document recordthat corresponds to the scope-related index key, wherein the documentrecord is used in providing results to the query such that the searchscope of the query is related to the scope-related index key when thequery is authored to included the search scope.
 12. The system of claim11, wherein the index further includes a first partition correspondingto index keys that are related to content of the documents and a secondpartition that corresponds to the scope-related index keys.
 13. Thesystem of claim 12, wherein the index further includes a third partitionthat includes additional document records organized according tocombinations of the scope-related index keys such that another searchscope is defined by the combination.
 14. The system of claim 11, whereinthe index is further configured to be updated when an additionaldocument is inserted amongst the documents that are queried such that anadditional document record is associated with the scope-related indexkey in the index when the additional document is associated withscope-related index key.
 15. The system of claim 11, further comprisingan interface for manually generating and manipulating additionalscope-related index keys from additional properties associated withadditional search scopes of the documents.
 16. A computer-readablemedium that includes computer-executable instructions for establishing asearch scope for a query of documents, the instructions comprising:identifying a property related to the documents, the property beingassociated with a scope of the documents; generating a scope-relatedindex key according to the identified property, wherein thescope-related index key is emitted among a set of other index keysassociated with a crawl of the documents; and generating an index thatincludes a first partition, a second partition, and a third partition;arranging the index to include document records related to content ofthe documents in the first partition and include document recordsrelated to the scope-related index key in the second partition, whereinthe document records are used in providing results to the query suchthat the search scope of the query is related to the scope-related indexkey when the query is authored to included the search scope associatedwith the scope-related index key.
 17. The computer-readable medium ofclaim 16, wherein arranging the index further comprises including athird partition that includes additional document records organizedaccording to combinations of the scope-related index keys such thatanother search scope is defined by the combination.
 18. Thecomputer-readable medium of claim 17, wherein the third partition isupdated when a new combination of scope-related index keys is created bycopying the third partition to create a new third partition whileinserting the document records into the new third partition thatcorrespond to the new combination.
 19. The computer-readable medium ofclaim 17, wherein the third partition is updated asynchronously to anupdate of the first partition and second partition.
 20. Thecomputer-readable medium of claim 16, wherein arranging the indexfurther comprises updating the index when an additional documentinserted amongst the documents that are queried, such that an additionaldocument record is associated with the scope-related index key when theadditional document is associated with the identified property.
 21. Thecomputer-readable medium of claim 16, wherein each of the documentrecords includes a document identifier that identifies the document forthe query.
 22. The computer-readable medium of claim 16, furthercomprising generating a scope selection according to the scope-relatedindex key such that the scope selection is selectable by a client forproviding a scope to a client generated query.
 23. The computer-readablemedium of claim 16, further comprising providing an interface formanually generating and manipulating additional scope-related index keysfrom additional properties associated with additional search scopes ofthe documents.